Playback device mode based on device base

ABSTRACT

Example techniques relate to changing a playback device mode based on a device base. In an example implementation, a first playback device operates in a first mode where it is connected to a first network and plays back audio content while in the first mode. The playback device detects connection of the first playback device to a device base and while the first playback device is on the device base, detects connection to a second network. The first playback device switches from operating in the first mode to operating in a second mode. The first playback device forms a stereo pair configuration with a second playback device over the second network in the second mode. While in the second mode, the first playback device plays back a first channel of audio content in synchrony with the second playback device playing back a second channel of the audio content.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C. § 120 to, and is acontinuation of, U.S. non-provisional patent application Ser. No.16/011,273, filed on Jun. 18, 2018, entitled “Playback System Join WithBase,” which is incorporated herein by reference in its entirety.

U.S. non-provisional patent application Ser. No. 16/011,273 claimspriority under 35 U.S.C. § 120 to, and is a continuation of, U.S.non-provisional patent application Ser. No. 14/844,253, filed on Sep. 3,2015, entitled “Playback System Join With Base,” and issued as U.S. Pat.No. 10,001,965 on which is incorporated herein by reference in itsentirety.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer goods and, more particularly, tomethods, systems, products, features, services, and other elementsdirected to media playback or some aspect thereof.

BACKGROUND

Options for accessing and listening to digital audio in an out-loudsetting were limited until in 2003, when SONOS, Inc. filed for one ofits first patent applications, entitled “Method for Synchronizing AudioPlayback between Multiple Networked Devices,” and began offering a mediaplayback system for sale in 2005. The Sonos Wireless HiFi System enablespeople to experience music from many sources via one or more networkedplayback devices. Through a software control application installed on asmartphone, tablet, or computer, one can play what he or she wants inany room that has a networked playback device. Additionally, using thecontroller, for example, different tracks can be streamed to each roomwith a playback device, rooms can be grouped together for synchronousplayback, or the same track can be heard in all rooms synchronously.

Given the ever growing interest in digital media, there continues to bea need to develop consumer-accessible technologies to further enhancethe listening experience.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technologymay be better understood with regard to the following description,appended claims, and accompanying drawings where:

FIG. 1 shows an example media playback system configuration in whichcertain embodiments may be practiced;

FIG. 2 shows a functional block diagram of an example playback device;

FIG. 3 shows a functional block diagram of an example control device;

FIG. 4 shows an example controller interface;

FIG. 5 shows an example playback device and an example device base;

FIG. 6 shows an example flow diagram to facilitate a playback devicejoining a media playback system, according to an example embodiment;

FIG. 7 shows another example media playback system configuration inwhich certain embodiments may be practiced;

FIG. 8 illustrates an example message flow between devices, according toan example embodiment;

FIG. 9 shows an example control device and controller interface,according to an example embodiment;

FIG. 10 shows an example flow diagram to facilitate transfer offavorites between media playback systems, according to an exampleembodiment;

FIG. 11 shows an example playback device, according to an exampleembodiment;

FIG. 12 shows an example control device and controller interface,according to an example embodiment; and

FIG. 13 shows another example flow diagram to facilitate a playbackdevice joining a media playback system, according to an exampleembodiment.

The drawings are for the purpose of illustrating example embodiments,but it is understood that the inventions are not limited to thearrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Overview

Embodiments described herein involve, inter alia, causing a playbackdevice joining a media playback system upon being placed upon a devicebase that is associated with the media playback system. An example mediaplayback may include one or more devices that are interconnected withone another to operate as a system. By joining a media playback system,a playback device may become associated with one or more second devicesof the media playback system. Further, the playback device may adopt aname and network parameters that allow the playback device tointerconnect and communicate with the one or more second devices.

Some media playback systems may include at least one of two or moretypes of devices. For instance, an example media playback system mayinclude one or more playback devices that play back media and perhapsalso one or more control devices that include respective controlinterfaces to control playback by the one or more playback devices. Acertain set of such devices may be associated with one another as amedia playback system such that the control device(s) are configured tocontrol playback by the playback device(s).

A media playback system may be referred to as a household, as an examplesystem may include one or more playback devices in different rooms of ahome (e.g., a house or apartment) or other building (e.g., an office).The media playback system may include one or more zones that include oneor more respective playback devices. Each zone may correspond to arespective room or area of the household. Upon being placed on aparticular device base of the media playback system, a playback devicemay join a given zone of the media playback system that is associatedwith that particular device base.

In practice, a playback device may detect that it is placed onto adevice base. The playback device may identify the device base as aparticular device base, which may in turn identify the media playbacksystem that is associated with the particular device base. In somecases, the playback device may identify the device base by way of asignal or message received from the device base.

After identifying the device base, the playback device may send arequest to join the media playback system that is associated with theparticular device base. In response to the request, the playback devicemay receive a message that enables the playback device to join theparticular media playback system. The message may include systemconfiguration and/or network parameters that allow the playback deviceto interconnect and communicate with the media playback system. Uponreceiving such a message, the playback device may automatically join themedia playback system by adopting the system configuration and networkparameters.

Some example playback devices might automatically join a media playbacksystem upon being placed on a device base when configured to do so (andperhaps might not join the media playback system when configured not todo so). For example, a playback device may include a tangible datastorage that includes a configuration of the playback device. Such aconfiguration may govern behavior of the playback device in certainsituations, such as whether the playback device automatically joins amedia playback system upon being placed on a device base that isassociated with the media playback system. In some cases, theconfiguration may be explicit (e.g., a setting is set to enable theplayback device to automatically join media playback systems (or one ormore particular media playback systems)). Alternatively, theconfiguration could be implicit. For instance, the playback device mightbe configured to join media playback systems when not be currently partof a media playback system, in factory reset mode, or in a portable mode(e.g., battery-powered), among other possible states.

According to some example configurations, the playback device may jointhe media playback system on a limited basis when automatically joiningbased on placement on a device base. A playback device that has joinedin such a manner may be referred to as a guest device. A guest devicemay have limited access to a media playback system, as compared withother playback devices that have joined the media playback system usingother techniques, such as explicit configuration). For instance, uponbeing placed on the device base, a playback device may join a mediaplayback system for a limited period of time or a limited number ofmedia item plays. After expiration of this period, the playback devicemay automatically leave the media playback system. Further, the playbackdevice may have limited access to other devices of the media playbacksystem or to services with which the media playback system isregistered.

In some embodiments, a device base of a media playback system mayinclude a controller that facilities a playback device joining the mediaplayback system when the playback device is placed upon a base of thedevice base. The device base may detect placement of the playback deviceonto its base, and responsively perform operations to join the playbackdevice to its media playback system. Such operations may includerequesting that the playback device join the media playback system orproviding an identifier of the device base to the playback device,perhaps to facilitate the playback device requesting that the playbackdevice join the media playback system. The operations might also includeproviding configuration information that enables the playback device tojoin the media playback system, among other possible operations.

Some playback devices may have favorites assigned to the playbackdevice. Such favorites may be accessible through a control interface(e.g., buttons) on the playback device itself and/or through a controlinterface on a control device. For instance, an example control devicemay include five favorite buttons. Selection of a particular favoritebutton may cause the playback device to begin playing back a particularmedia source (e.g., a track, album, playlist, or internet radiostation). In some cases, the favorites assigned to a given playbackdevice may have been configured when the playback device was joined to afirst media playback system. Upon being placed on a device base that isassociated with a second media playback system, the playback device mayautomatically join the second media playback system.

However, the second media playback system might not have access to thesame media as the first media playback device. To retain access to thefavorite, the playback device may cross-link the favorite media from thefirst system with media that the second system has access. For instance,a favorite might be linked to a playlist of media items from a firstmedia service (e.g., Spotify®). If the second system is not registeredwith the first media service, the playback device may search forversions of the media items from one or more second services (e.g.,Apple Music® or Tidal®). In this way, the favorite may continue to linkto the same playlist of media items when the playback device is part ofthe second media playback system, albeit from one or more differentsources.

As indicated above, example techniques may involve a playback devicejoining a media playback system when placed upon a device base. In oneaspect, a method is provided. The method may involve detecting placementof the playback device onto a device base of a particular media playbacksystem. The method may further involve determining that the playbackdevice is configured to automatically join media playback systems. Themethod may also involve sending, to the particular media playbacksystem, a request to join the particular media playback system based ondetermining that the playback device is configured to automatically joinmedia playback systems. The method may further involve receiving, fromthe media playback system, one or more messages that enable the playbackdevice to join the particular media playback system.

In another aspect, a device is provided. The device includes one or moreprocessors; and a data storage having stored therein instructionsexecutable by the one or more processors to cause the playback device toperform operations. The operations may include detecting placement ofthe playback device onto a device base of a particular media playbacksystem. The operations may further include determining that the playbackdevice is configured to automatically join media playback systems. Theoperations may also include sending, to the particular media playbacksystem, a request to join the particular media playback system based ondetermining that the playback device is configured to automatically joinmedia playback systems. The operations may further include receiving,from the media playback system, one or more messages that enable theplayback device to join the particular media playback system.

In yet another aspect, a non-transitory computer readable memory isprovided. The non-transitory computer readable memory has stored thereoninstructions executable by a computing device to cause the computingdevice to perform operations. The operations may include detectingplacement of the playback device onto a device base of a particularmedia playback system. The operations may further include determiningthat the playback device is configured to automatically join mediaplayback systems. The operations may also include sending, to theparticular media playback system, a request to join the particular mediaplayback system based on determining that the playback device isconfigured to automatically join media playback systems. The operationsmay further include receiving, from the media playback system, one ormore messages that enable the playback device to join the particularmedia playback system.

Example techniques may involve a device base facilitating a playbackdevice joining a media playback system when the playback device isplaced upon the device base. In one aspect, a method is provided. Themethod may involve detecting placement of a playback device onto thebase. The method may also involve, responsively, listening for a requestto join media playback systems. The method may further involve sending,to a media playback system that is associated with the device base, arequest to join the playback device to the media playback system uponreceiving the request to join media playback systems from the playbackdevice. The method may additionally involve receiving, from the mediaplayback system, a message indicating that the playback device ispermitted to join the media playback system, and responsively, sending amessage that enables the playback device to join the media playbacksystem.

In another aspect, a device base is provided. The device base includesone or more processors; and a data storage having stored thereininstructions executable by the one or more processors to cause thedevice base to perform operations. The operations may include detectingplacement of a playback device onto the base. The operations may alsoinclude, responsively, listening for a request to join media playbacksystems. The operations may further include sending, to a media playbacksystem that is associated with the device base, a request to join theplayback device to the media playback system upon receiving the requestto join media playback systems from the playback device. The operationsmay additionally include receiving, from the media playback system, amessage indicating that the playback device is permitted to join themedia playback system, and responsively, sending a message that enablesthe playback device to join the media playback system.

In yet another aspect, a non-transitory computer readable memory isprovided. The non-transitory computer readable memory has stored thereoninstructions executable by a device base to cause the device base toperform operations. The operations may include detecting placement of aplayback device onto the base. The operations may also include,responsively, listening for a request to join media playback systems.The operations may further include sending, to a media playback systemthat is associated with the device base, a request to join the playbackdevice to the media playback system upon receiving the request to joinmedia playback systems from the playback device. The operations mayadditionally include receiving, from the media playback system, amessage indicating that the playback device is permitted to join themedia playback system, and responsively, sending a message that enablesthe playback device to join the media playback system.

It will be understood by one of ordinary skill in the art that thisdisclosure includes numerous other embodiments. It will be understood byone of ordinary skill in the art that this disclosure includes numerousother embodiments. While some examples described herein may refer tofunctions performed by given actors such as “users” and/or otherentities, it should be understood that this description is for purposesof explanation only. The claims should not be interpreted to requireaction by any such example actor unless explicitly required by thelanguage of the claims themselves.

II. Example Operating Environment

FIG. 1 illustrates an example configuration of a media playback system100A in which one or more embodiments disclosed herein may be practicedor implemented. The media playback system 100A as shown is associatedwith an example home environment having several rooms and spaces, suchas for example, a master bedroom, an office, a dining room, and a livingroom. As shown in the example of FIG. 1, the media playback system 100Aincludes playback devices 102-124, control devices 126 and 128, and awired or wireless network router 130.

Further discussions relating to the different components of the examplemedia playback system 100A and how the different components may interactto provide a user with a media experience may be found in the followingsections. While discussions herein may generally refer to the examplemedia playback system 100A, technologies described herein are notlimited to applications within, among other things, the home environmentas shown in FIG. 1. For instance, the technologies described herein maybe useful in environments where multi-zone audio may be desired, suchas, for example, a commercial setting like a restaurant, mall orairport, a vehicle like a sports utility vehicle (SUV), bus or car, aship or boat, an airplane, and so on.

a. Example Playback Devices

FIG. 2 shows a functional block diagram of an example playback device200 that may be configured to be one or more of the playback devices102-124 of the media playback system 100A of FIG. 1. The playback device200 may include a processor 202, software components 204, memory 206,audio processing components 208, audio amplifier(s) 210, speaker(s) 212,a network interface 214 including wireless interface(s) 216 and wiredinterface(s) 218, and a power supply 220, which may include an AC/DCconverter 222 and/or one or more batteries 224.

In one case, the playback device 200 may not include the speaker(s) 212,but rather a speaker interface for connecting the playback device 200 toexternal speakers. In another case, the playback device 200 may includeneither the speaker(s) 212 nor the audio amplifier(s) 210, but rather anaudio interface for connecting the playback device 200 to an externalaudio amplifier or audio-visual receiver.

In one example, the processor 202 may be a clock-driven computingcomponent configured to process input data according to instructionsstored in the memory 206. The memory 206 may be a tangiblecomputer-readable medium configured to store instructions executable bythe processor 202. For instance, the memory 206 may be data storage thatcan be loaded with one or more of the software components 204 executableby the processor 202 to achieve certain functions. In one example, thefunctions may involve the playback device 200 retrieving audio data froman audio source or another playback device. In another example, thefunctions may involve the playback device 200 sending audio data toanother device or playback device on a network. In yet another example,the functions may involve pairing of the playback device 200 with one ormore playback devices to create a multi-channel audio environment.

Certain functions may involve the playback device 200 synchronizingplayback of audio content with one or more other playback devices.During synchronous playback, a listener will preferably not be able toperceive time-delay differences between playback of the audio content bythe playback device 200 and the one or more other playback devices. U.S.Pat. No. 8,234,395 entitled, “System and method for synchronizingoperations among a plurality of independently clocked digital dataprocessing devices,” which is hereby incorporated by reference, providesin more detail some examples for audio playback synchronization amongplayback devices.

The memory 206 may further be configured to store data associated withthe playback device 200, such as one or more zones and/or zone groupsthe playback device 200 is a part of, audio sources accessible by theplayback device 200, or a playback queue that the playback device 200(or some other playback device) may be associated with. The data may bestored as one or more state variables that are periodically updated andused to describe the state of the playback device 200. The memory 206may also include the data associated with the state of the other devicesof the media system, and shared from time to time among the devices sothat one or more of the devices have the most recent data associatedwith the system. Other embodiments are also possible.

The audio processing components 208 may include one or moredigital-to-analog converters (DAC), an audio preprocessing component, anaudio enhancement component or a digital signal processor (DSP), and soon. In one embodiment, one or more of the audio processing components208 may be a subcomponent of the processor 202. In one example, audiocontent may be processed and/or intentionally altered by the audioprocessing components 208 to produce audio signals. The produced audiosignals may then be provided to the audio amplifier(s) 210 foramplification and playback through speaker(s) 212. Particularly, theaudio amplifier(s) 210 may include devices configured to amplify audiosignals to a level for driving one or more of the speakers 212. Thespeaker(s) 212 may include an individual transducer (e.g., a “driver”)or a complete speaker system involving an enclosure with one or moredrivers. A particular driver of the speaker(s) 212 may include, forexample, a subwoofer (e.g., for low frequencies), a mid-range driver(e.g., for middle frequencies), and/or a tweeter (e.g., for highfrequencies). In some cases, each transducer in the one or more speakers212 may be driven by an individual corresponding audio amplifier of theaudio amplifier(s) 210. In addition to producing analog signals forplayback by the playback device 200, the audio processing components 208may be configured to process audio content to be sent to one or moreother playback devices for playback.

Audio content to be processed and/or played back by the playback device200 may be received from an external source, such as via an audioline-in input connection (e.g., an auto-detecting 3.5 mm audio line-inconnection) or the network interface 214.

The network interface 214 may be configured to facilitate a data flowbetween the playback device 200 and one or more other devices on a datanetwork. As such, the playback device 200 may be configured to receiveaudio content over the data network from one or more other playbackdevices in communication with the playback device 200, network deviceswithin a local area network, or audio content sources over a wide areanetwork such as the Internet. In one example, the audio content andother signals transmitted and received by the playback device 200 may betransmitted in the form of digital packet data containing an InternetProtocol (IP)-based source address and IP-based destination addresses.In such a case, the network interface 214 may be configured to parse thedigital packet data such that the data destined for the playback device200 is properly received and processed by the playback device 200.

As shown, the network interface 214 may include wireless interface(s)216 and wired interface(s) 218. The wireless interface(s) 216 mayprovide network interface functions for the playback device 200 towirelessly communicate with other devices (e.g., other playbackdevice(s), speaker(s), receiver(s), network device(s), control device(s)within a data network the playback device 200 is associated with) inaccordance with a communication protocol (e.g., any wireless standardincluding IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4Gmobile communication standard, and so on). The wired interface(s) 218may provide network interface functions for the playback device 200 tocommunicate over a wired connection with other devices in accordancewith a communication protocol (e.g., IEEE 802.3). While the networkinterface 214 shown in FIG. 2 includes both wireless interface(s) 216and wired interface(s) 218, the network interface 214 may in someembodiments include only wireless interface(s) or only wiredinterface(s).

The power supply 220 may supply current to the various other componentsof the playback device 200. The power supply 220 may include an AC/DCconverter 222, which may convert supplied alternating current to directcurrent used by the component of playback device 220. In some cases,playback 220 may include one or more batteries 224, which may storecharge that the playback device 200 draws during portable operation.

In one example, the playback device 200 and one other playback devicemay be paired to play two separate audio components of audio content.For instance, playback device 200 may be configured to play a leftchannel audio component, while the other playback device may beconfigured to play a right channel audio component, thereby producing orenhancing a stereo effect of the audio content. The paired playbackdevices (also referred to as “bonded playback devices”) may further playaudio content in synchrony with other playback devices.

In another example, the playback device 200 may be sonicallyconsolidated with one or more other playback devices to form a single,consolidated playback device. A consolidated playback device may beconfigured to process and reproduce sound differently than anunconsolidated playback device or playback devices that are paired,because a consolidated playback device may have additional speakerdrivers through which audio content may be rendered. For instance, ifthe playback device 200 is a playback device designed to render lowfrequency range audio content (i.e. a subwoofer), the playback device200 may be consolidated with a playback device designed to render fullfrequency range audio content. In such a case, the full frequency rangeplayback device, when consolidated with the low frequency playbackdevice 200, may be configured to render only the mid and high frequencycomponents of audio content, while the low frequency range playbackdevice 200 renders the low frequency component of the audio content. Theconsolidated playback device may further be paired with a singleplayback device or yet another consolidated playback device.

By way of illustration, SONOS, Inc. presently offers (or has offered)for sale certain playback devices including a “PLAY:1,” “PLAY:3,”“PLAY:5,” “PLAYBAR,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any otherpast, present, and/or future playback devices may additionally oralternatively be used to implement the playback devices of exampleembodiments disclosed herein. Additionally, it is understood that aplayback device is not limited to the example illustrated in FIG. 2 orto the SONOS product offerings. For example, a playback device mayinclude a wired or wireless headphone. In another example, a playbackdevice may include or interact with a docking station for personalmobile media playback devices. In yet another example, a playback devicemay be integral to another device or component such as a television, alighting fixture, or some other device for indoor or outdoor use.

b. Example Playback Zone Configurations

Referring back to the media playback system 100A of FIG. 1, theenvironment may have one or more playback zones, each with one or moreplayback devices. The media playback system 100A may be established withone or more playback zones, after which one or more zones may be added,or removed to arrive at the example configuration shown in FIG. 1. Eachzone may be given a name according to a different room or space such asan office, bathroom, master bedroom, bedroom, kitchen, dining room,living room, and/or balcony. In one case, a single playback zone mayinclude multiple rooms or spaces. In another case, a single room orspace may include multiple playback zones.

As shown in FIG. 1, the balcony, dining room, kitchen, bathroom, office,and bedroom zones each have one playback device, while the living roomand master bedroom zones each have multiple playback devices. In theliving room zone, playback devices 104, 106, 108, and 110 may beconfigured to play audio content in synchrony as individual playbackdevices, as one or more bonded playback devices, as one or moreconsolidated playback devices, or any combination thereof. Similarly, inthe case of the master bedroom, playback devices 122 and 124 may beconfigured to play audio content in synchrony as individual playbackdevices, as a bonded playback device, or as a consolidated playbackdevice.

In one example, one or more playback zones in the environment of FIG. 1may each be playing different audio content. For instance, the user maybe grilling in the balcony zone and listening to hip hop music beingplayed by the playback device 102 while another user may be preparingfood in the kitchen zone and listening to classical music being playedby the playback device 114. In another example, a playback zone may playthe same audio content in synchrony with another playback zone. Forinstance, the user may be in the office zone where the playback device118 is playing the same rock music that is being playing by playbackdevice 102 in the balcony zone. In such a case, playback devices 102 and118 may be playing the rock music in synchrony such that the user mayseamlessly (or at least substantially seamlessly) enjoy the audiocontent that is being played out-loud while moving between differentplayback zones. Synchronization among playback zones may be achieved ina manner similar to that of synchronization among playback devices, asdescribed in previously referenced U.S. Pat. No. 8,234,395.

As suggested above, the zone configurations of the media playback system100A may be dynamically modified, and in some embodiments, the mediaplayback system 100A supports numerous configurations. For instance, ifa user physically moves one or more playback devices to or from a zone,the media playback system 100A may be reconfigured to accommodate thechange(s). For instance, if the user physically moves the playbackdevice 102 from the balcony zone to the office zone, the office zone maynow include both the playback device 118 and the playback device 102.The playback device 102 may be paired or grouped with the office zoneand/or renamed if so desired via a control device such as the controldevices 126 and 128. On the other hand, if the one or more playbackdevices are moved to a particular area in the home environment that isnot already configured with a playback zone, a new playback zone may becreated for the particular area.

Further, different playback zones of the media playback system 100A maybe dynamically combined into zone groups or split up into individualplayback zones. For instance, the Dining Room zone and the Kitchen zone114 may be combined into a zone group for a dinner party such thatplayback devices 112 and 114 may render audio content in synchrony. Onthe other hand, the living room zone may be split into a television zoneincluding playback device 104, and a listening zone including playbackdevices 106, 108, and 110, if the user wishes to listen to music in theliving room space while another user wishes to watch television.

c. Example Control Devices

FIG. 3 shows a functional block diagram of an example control device 300that may be configured to be one or both of the control devices 126 and128 of the media playback system 100A. Control device 300 may also bereferred to as a controller 300. As shown, the control device 300 mayinclude a processor 302, memory 304, a network interface 306, and a userinterface 308. In one example, the control device 300 may be a dedicatedcontroller for the media playback system 100A. In another example, thecontrol device 300 may be a network device on which media playbacksystem controller application software may be installed, such as forexample, an iPhone™ iPad™ or any other smart phone, tablet or networkdevice (e.g., a networked computer such as a PC or Mac™).

The processor 302 may be configured to perform functions relevant tofacilitating user access, control, and configuration of the mediaplayback system 100A. The memory 304 may be configured to storeinstructions executable by the processor 302 to perform those functions.The memory 304 may also be configured to store the media playback systemcontroller application software and other data associated with the mediaplayback system 100A and the user.

In one example, the network interface 306 may be based on an industrystandard (e.g., infrared, radio, wired standards including IEEE 802.3,wireless standards including IEEE 802.11a, 802.11b, 802.11g, 802.11n,802.11ac, 802.15, 4G mobile communication standard, and so on). Thenetwork interface 306 may provide a means for the control device 300 tocommunicate with other devices in the media playback system 100A. In oneexample, data and information (e.g., such as a state variable) may becommunicated between control device 300 and other devices via thenetwork interface 306. For instance, playback zone and zone groupconfigurations in the media playback system 100A may be received by thecontrol device 300 from a playback device or another network device, ortransmitted by the control device 300 to another playback device ornetwork device via the network interface 306. In some cases, the othernetwork device may be another control device.

Playback device control commands such as volume control and audioplayback control may also be communicated from the control device 300 toa playback device via the network interface 306. As suggested above,changes to configurations of the media playback system 100A may also beperformed by a user using the control device 300. The configurationchanges may include adding/removing one or more playback devices to/froma zone, adding/removing one or more zones to/from a zone group, forminga bonded or consolidated player, separating one or more playback devicesfrom a bonded or consolidated player, among others. Accordingly, thecontrol device 300 may sometimes be referred to as a controller, whetherthe control device 300 is a dedicated controller or a network device onwhich media playback system controller application software isinstalled.

The user interface 308 of the control device 300 may be configured tofacilitate user access and control of the media playback system 100A, byproviding a controller interface such as the controller interface 400shown in FIG. 4. The controller interface 400 includes a playbackcontrol region 410, a playback zone region 420, a playback status region430, a playback queue region 440, and an audio content sources region450. The user interface 400 as shown is just one example of a userinterface that may be provided on a network device such as the controldevice 300 of FIG. 3 (and/or the control devices 126 and 128 of FIG. 1)and accessed by users to control a media playback system such as themedia playback system 100A. Other user interfaces of varying formats,styles, and interactive sequences may alternatively be implemented onone or more network devices to provide comparable control access to amedia playback system.

The playback control region 410 may include selectable (e.g., by way oftouch or by using a cursor) icons to cause playback devices in aselected playback zone or zone group to play or pause, fast forward,rewind, skip to next, skip to previous, enter/exit shuffle mode,enter/exit repeat mode, enter/exit cross fade mode. The playback controlregion 410 may also include selectable icons to modify equalizationsettings, and playback volume, among other possibilities.

The playback zone region 420 may include representations of playbackzones within the media playback system 100A. In some embodiments, thegraphical representations of playback zones may be selectable to bringup additional selectable icons to manage or configure the playback zonesin the media playback system, such as a creation of bonded zones,creation of zone groups, separation of zone groups, and renaming of zonegroups, among other possibilities.

For example, as shown, a “group” icon may be provided within each of thegraphical representations of playback zones. The “group” icon providedwithin a graphical representation of a particular zone may be selectableto bring up options to select one or more other zones in the mediaplayback system to be grouped with the particular zone. Once grouped,playback devices in the zones that have been grouped with the particularzone will be configured to play audio content in synchrony with theplayback device(s) in the particular zone. Analogously, a “group” iconmay be provided within a graphical representation of a zone group. Inthis case, the “group” icon may be selectable to bring up options todeselect one or more zones in the zone group to be removed from the zonegroup. Other interactions and implementations for grouping andungrouping zones via a user interface such as the user interface 400 arealso possible. The representations of playback zones in the playbackzone region 420 may be dynamically updated as playback zone or zonegroup configurations are modified.

The playback status region 430 may include graphical representations ofaudio content that is presently being played, previously played, orscheduled to play next in the selected playback zone or zone group. Theselected playback zone or zone group may be visually distinguished onthe user interface, such as within the playback zone region 420 and/orthe playback status region 430. The graphical representations mayinclude track title, artist name, album name, album year, track length,and other relevant information that may be useful for the user to knowwhen controlling the media playback system via the user interface 400.

The playback queue region 440 may include graphical representations ofaudio content in a playback queue associated with the selected playbackzone or zone group. In some embodiments, each playback zone or zonegroup may be associated with a playback queue containing informationcorresponding to zero or more audio items for playback by the playbackzone or zone group. For instance, each audio item in the playback queuemay comprise a uniform resource identifier (URI), a uniform resourcelocator (URL) or some other identifier that may be used by a playbackdevice in the playback zone or zone group to find and/or retrieve theaudio item from a local audio content source or a networked audiocontent source, possibly for playback by the playback device.

In one example, a playlist may be added to a playback queue, in whichcase information corresponding to each audio item in the playlist may beadded to the playback queue. In another example, audio items in aplayback queue may be saved as a playlist. In a further example, aplayback queue may be empty, or populated but “not in use” when theplayback zone or zone group is playing continuously streaming audiocontent, such as Internet radio that may continue to play untilotherwise stopped, rather than discrete audio items that have playbackdurations. In an alternative embodiment, a playback queue can includeInternet radio and/or other streaming audio content items and be “inuse” when the playback zone or zone group is playing those items. Otherexamples are also possible.

When playback zones or zone groups are “grouped” or “ungrouped,”playback queues associated with the affected playback zones or zonegroups may be cleared or re-associated. For example, if a first playbackzone including a first playback queue is grouped with a second playbackzone including a second playback queue, the established zone group mayhave an associated playback queue that is initially empty, that containsaudio items from the first playback queue (such as if the secondplayback zone was added to the first playback zone), that contains audioitems from the second playback queue (such as if the first playback zonewas added to the second playback zone), or a combination of audio itemsfrom both the first and second playback queues. Subsequently, if theestablished zone group is ungrouped, the resulting first playback zonemay be re-associated with the previous first playback queue, or beassociated with a new playback queue that is empty or contains audioitems from the playback queue associated with the established zone groupbefore the established zone group was ungrouped. Similarly, theresulting second playback zone may be re-associated with the previoussecond playback queue, or be associated with a new playback queue thatis empty, or contains audio items from the playback queue associatedwith the established zone group before the established zone group wasungrouped. Other examples are also possible.

Referring back to the user interface 400 of FIG. 4, the graphicalrepresentations of audio content in the playback queue region 440 mayinclude track titles, artist names, track lengths, and other relevantinformation associated with the audio content in the playback queue. Inone example, graphical representations of audio content may beselectable to bring up additional selectable icons to manage and/ormanipulate the playback queue and/or audio content represented in theplayback queue. For instance, a represented audio content may be removedfrom the playback queue, moved to a different position within theplayback queue, or selected to be played immediately, or after anycurrently playing audio content, among other possibilities. A playbackqueue associated with a playback zone or zone group may be stored in amemory on one or more playback devices in the playback zone or zonegroup, on a playback device that is not in the playback zone or zonegroup, and/or some other designated device. Playback of such a playbackqueue may involve one or more playback devices playing back media itemsof the queue, perhaps in sequential or random order.

The audio content sources region 450 may include graphicalrepresentations of selectable audio content sources from which audiocontent may be retrieved and played by the selected playback zone orzone group. Discussions pertaining to audio content sources may be foundin the following section.

d. Example Audio Content Sources

As indicated previously, one or more playback devices in a zone or zonegroup may be configured to retrieve for playback audio content (e.g.,according to a corresponding URI or URL for the audio content) from avariety of available audio content sources. In one example, audiocontent may be retrieved by a playback device directly from acorresponding audio content source (e.g., a line-in connection). Inanother example, audio content may be provided to a playback device overa network via one or more other playback devices or network devices.

Example audio content sources may include a memory of one or moreplayback devices in a media playback system such as the media playbacksystem 100A of FIG. 1, local music libraries on one or more networkdevices (such as a control device, a network-enabled personal computer,or a networked-attached storage (NAS), for example), streaming audioservices providing audio content via the Internet (e.g., the cloud), oraudio sources connected to the media playback system via a line-in inputconnection on a playback device or network devise, among otherpossibilities.

In some embodiments, audio content sources may be regularly added orremoved from a media playback system such as the media playback system100A of FIG. 1. In one example, an indexing of audio items may beperformed whenever one or more audio content sources are added, removedor updated. Indexing of audio items may involve scanning foridentifiable audio items in all folders/directory shared over a networkaccessible by playback devices in the media playback system, andgenerating or updating an audio content database containing metadata(e.g., title, artist, album, track length, among others) and otherassociated information, such as a URI or URL for each identifiable audioitem found. Other examples for managing and maintaining audio contentsources may also be possible.

e. Example Device Base

FIG. 5 shows an example playback device 500 and an example device base502. As shown, playback device 500 may be placed onto device base 502.Protrusions 504A and 504B may align with recesses 506A and 508B on theplayback device. Such protrusions and recesses may facilitate placingthe playback device 500 on the device 502 and may improve stability ofthe playback device while it is positioned on the device base 502.

Some device bases may include device charging systems. For instance,device base 502 includes charging system 508. When a playback device,such as playback device 500, is placed on device base 502, the playbackdevice may draw current from charging system 508 to charge one or moreof its batteries. In some embodiments, charging system 508 may includean inductive charging circuit (e.g., a coil that induces a current in acorresponding coil in the playback device that wirelessly charges one ormore batteries of the playback device). Alternatively, charging system508 may include conductive terminals by which playback device 500 maydraw current from the device base 502.

In some embodiments, a device base may carry an identifier thatdistinguishes that device base from at least some other device bases(e.g., other device bases of a given media playback system, or perhapsother devices bases more broadly). In some implementations, the devicebase may passively communicate this identifier to a playback device thatis placed upon the device base. For instance, a charging circuit mayinclude a current or voltage signature (i.e., a pattern) that is uniqueas compared to other device bases. A playback device may use this uniquesignature to identify the charging base. Alternatively, a chargingcircuit may superimpose a signal onto the current delivered from thedevice base (e.g., current from the device base may include a higherfrequency signal carrying the identifier of the device base). In furtherexamples, a device base may include an RFID tag, QR code, or otheridentifying component that is read by the playback device when theplayback device is placed upon the device base.

In some implementations, a device base includes a control system. Forexample, device base 502 includes control system 510. Control system 510includes one or more processors and a memory. The processor(s) may beclock-driven computing components that process input data according toinstructions stored in the memory. The memory may be a tangiblecomputer-readable medium configured to store instructions executable bythe processor(s) to cause the device base to carry out operations.Example operations include communicating via a communications interface(e.g., a BLUETOOTH® interface) with playback device 500 and causingcharging system 508 to supply current to playback device 500, amongother examples.

Moving now to several example implementations, implementations 600,1000, and 1300 shown in FIGS. 6, 10, and 13, respectively presentexample embodiments of techniques described herein. These exampleembodiments that can be implemented within an operating environmentincluding, for example, the media playback system 100 of FIG. 1, one ormore of the playback device 200 of FIG. 2, or one or more of the controldevice 300 of FIG. 3. Further, operations illustrated by way of exampleas being performed by a media playback system can be performed by anysuitable device, such as a playback device or a control device of amedia playback system. Implementations 600, 1000, and 1300 may includeone or more operations, functions, or actions as illustrated by one ormore of blocks shown in FIGS. 6, 10, and 13. Although the blocks areillustrated in sequential order, these blocks may also be performed inparallel, and/or in a different order than those described herein. Also,the various blocks may be combined into fewer blocks, divided intoadditional blocks, and/or removed based upon the desired implementation.

In addition, for the implementations disclosed herein, the flowchartsshow functionality and operation of one possible implementation ofpresent embodiments. In this regard, each block may represent a module,a segment, or a portion of program code, which includes one or moreinstructions executable by a processor for implementing specific logicalfunctions or steps in the process. The program code may be stored on anytype of computer readable medium, for example, such as a storage deviceincluding a disk or hard drive. The computer readable medium may includenon-transitory computer readable medium, for example, such ascomputer-readable media that stores data for short periods of time likeregister memory, processor cache, and Random Access Memory (RAM). Thecomputer readable medium may also include non-transitory media, such assecondary or persistent long term storage, like read only memory (ROM),optical or magnetic disks, compact-disc read only memory (CD-ROM), forexample. The computer readable media may also be any other volatile ornon-volatile storage systems. The computer readable medium may beconsidered a computer readable storage medium, for example, or atangible storage device. In addition, for the implementations disclosedherein, each block may represent circuitry that is wired to perform thespecific logical functions in the process.

III. Example Techniques to Join a Playback Device to a Device Base

As discussed above, embodiments described herein may facilitate aplayback device joining a media playback system when placed onto adevice base. FIG. 6 illustrates an example implementation 600 by which aplayback device joins a media playback system when placed upon a devicebase that is associated with the device base.

a. Detect Placement of a Playback Device onto a Device Base of a MediaPlayback System

At block 602, implementation 600 involves detecting placement of theplayback device on a device base. For instance, referring to FIG. 5,playback device 500 may detect that it has been placed onto device base502. Device base 502 may be associated with a particular media playbacksystem (e.g., media playback system 100 of FIG. 1).

In some embodiments, a playback device may detect placement onto adevice base by way of a physical trigger. For instance, a device basemay be designed to trigger a switch or other mechanism of the devicebase when a playback device is placed upon the device base. In suchcases, by detecting triggering of the switch or mechanism, the playbackdevice detects placement onto the device base. As another example, aplayback device may detect placement onto a device base upon receivingcurrent from the device base (such when charging a battery of theplayback device from a device base).

Alternatively, a playback device may detect placement onto a device baseby way of a radio signal between the playback device and the devicebase. For instance, the playback device and the device base may includerespective radio interfaces (e.g., near-field wireless communicationsinterfaces such as NFC (near field communications) or BLUETOOTH® LE). Aplayback device may detect placement onto a device base upon receiving amessage from the device base.

The message may include an identifier of the device base. The playbackdevice may use the identifier to identify the media playback system thatthe device base is associated with (i.e., that the device base isassociated with a particular media playback system). In someembodiments, a playback device may identify the device base by way of anidentifier that uniquely identifies a particular base among devices of amedia playback system (and possibly among all device bases from aparticular manufacturer). In some implementations, each device base hassuch an identifier, which may be communicated to a playback device whenthat playback device is placed on the base. Within examples, theidentifier may be stored in a data storage of the device base (e.g., amemory of control system 510 of device base 502), or the identifier maybe coded into the device base (e.g., by way of a DIP switch or otherlogical circuitry). While several example techniques for identifying adevice base are noted, other techniques for identifying a device baseare contemplated as well, such as an RFID tag or QR code.

To illustrate, while playback device 500 is placed on device base 502,control system 510 may cause a radio interface to periodically transmitthe identifier of device base 502 to a corresponding radio interface ofplayback device 500. As noted above, a device base may use a near-fieldwireless communications interface, which may have a limited range suchthat the playback device is in range of the device base when theplayback device is placed on or nearby the device base. Shielding theantenna of such a communications interface may further limit and orientits communications range, which may prevent communications between aplayback device and a device base when the playback device is not on thedevice base such that successful communication between the playbackdevice and device base indicates that the playback device is placed uponthe device base.

In other examples, a signal may be communicated to the playback devicevia the charging circuit of the device base. For instance, a chargingcircuit may include a current or voltage signature (i.e., a pattern)that is unique as compared to other device bases. A playback device mayuse this unique signature to identify the charging base. Alternatively,a charging circuit may superimpose a communications signal onto thecurrent delivered from the device base (e.g., current from the devicebase may include a higher frequency communications signal carrying theidentifier).

FIG. 7 illustrates example media playback system 100B, which is anotherexample configuration of media playback system 100A. As shown in FIG. 7,media playback system 100B includes device bases 132, 134, 136, and 138.Playback devices 106, 108, 112, and 114 are placed on device bases 132,134, 136, and 138 respectively. When playback devices 106 and 108 areplaced upon respective device bases (e.g., device base 132 and 134),playback devices 106 and 108 may detect that they are placed upon thosedevice bases (i.e., device base 132 and 134) and perhaps also identifythose device bases. Likewise, when playback device 112 is placed on adevice base (e.g., device base 136), playback device 112 may identifythat device base. In another example, playback device 112 may be placedon device base 138 (after playback device 114 is removed) and identifythat device base.

b. Determine that the Playback Device is Configured to AutomaticallyJoin Media Playback Systems

Referring back to FIG. 6, at block 604, implementation 600 involvesdetermining that the playback device is configured to automatically joinmedia playback systems. For instance, after detecting placement ontodevice base 502, playback device 500 may determine whether playbackdevice 500 is configured to automatically join the media playbacksystems when placed upon a device base. As noted above, some exampleplayback devices might not automatically join a media playback systemupon being placed on a device base unless configured to do so. Theconfiguration may be explicit (e.g., a setting is set to configure theplayback device to automatically join media playback systems (or one ormore particular media playback systems)). Alternatively, theconfiguration could be implicit. For example, a device might beconfigured to join media playback systems when not be currently part ofa media playback system, when in a factory reset mode, or when in aportable mode (e.g., battery-powered), among other possible modes.

A configuration of a playback device may govern or influence whether theplayback device is configured to automatically join media playbacksystems. Such a configuration may be stored in tangible data storage ofthe playback device. For instance, in FIG. 2, playback device 200includes a memory, which may store a configuration of playback device200. Such a configuration may govern behavior of the playback device incertain situations, such as whether the playback device automaticallyjoins a media playback system upon being placed on a device base that isassociated with the media playback system. In some cases, such aconfiguration may permit a playback device to automatically join anymedia playback system. Alternatively, the configuration may restrict theplayback device to automatically join one or more particular mediaplayback systems (e.g., one or more media playback systems havingparticular names or identifiers).

Changes to this configuration may be made by a control device that isconnected to the playback devices, or in some implementations, using acontrol interface of the playback device. As described above inconnection to FIG. 3, a control device may include a control interfacethat includes various controls that control operation of a playbackdevice, which may include changes to the configuration of a playbackdevice.

Whether a given playback device is configured to automatically join themedia playback systems may depend upon whether the playback is currentlyjoined to another media playback system. If a playback device iscurrently joined to a first media playback system, the device may beconfigured not to automatically join a second media playback system whenplaced upon a playback device that is associated with the second mediaplayback system. However, if a playback device is not currently joinedto any media playback system, the device may be configured toautomatically join a media playback system when placed upon a playbackdevice that is associated with that media playback system. A playbackdevice may leave a media playback system when explicitly configured todo so (e.g., by way of a control interface) or when disconnected fromthe media playback system (e.g., the playback device is disconnectedfrom the other devices of the system). Further, a new playback device,or a device in factory reset mode, might not be connected to any mediaplayback system such that it is configured to automatically join mediaplayback systems.

Some media playback systems may require a password, an authenticationtoken, or other security mechanism from the playback device toautomatically join the media playback system. A password orauthentication token that authenticates a playback device to join aparticular media playback system may be stored on a playback device suchthat when the playback device is placed on a device base of that system,the pre-stored password or token authenticates the playback device tojoin the system.

In some embodiments, a configuration of a given playback device may bestored as one or more state variables that are stored in a data storagethat is maintained on another device or system that is accessible to theplayback device. For instance, in some cases, the media playback systemitself may store the state variables, perhaps in data storage of one ormore playback device(s) or control device(s) of a media playback system,perhaps within a database. Alternatively, a remote server (e.g., aserver that provides a cloud service) may store the state variables.Other examples are possible as well.

In some embodiments, the state variable(s) may be stored concurrently onmultiple devices (e.g., on multiple devices within the media playbacksystem), which may provide various advantages, such as redundancy andquicker access, among others. For instance, updates to the statevariables stored on one playback device may be transmitted to otherdevices within the media playback system, so as to maintain anup-to-date instance of the state variables on multiple devices. In suchcases, to determine whether a particular base is assigned a zoneproperty that is associated with a given zone of a media playbacksystem, a playback device may request (and receive) a state variablefrom one (or more) playback devices of the media playback system,perhaps by way of its network interface.

c. Send a Request to Join the Media Playback System

In FIG. 6, at block 606, implementation 600 involves sending a requestto join the media playback system. For example, playback device 500 maysend a request to join the particular media playback system to whichdevice base 502 is associated. In some embodiments, playback device 500may send such a request automatically, perhaps in response to detectingplacement upon device base 502 or in response to determining thatplayback device 500 is configured to automatically join media playbacksystems.

In some implementations, the playback device may broadcast the requestto join the media playback system such that devices of the mediaplayback system may receive the request. The playback device may sendthe broadcast according to a particular protocol, such as SONOS®Netstart or APPLE® Wireless Accessory Configuration (WAC). In operation,devices of a media playback system may listen for messages conforming tosuch a protocol. Further, such protocols may permit the playback deviceto communicate with the devices of the media playback system withoutbeing connected to the network that interconnects the devices.

In other implementations, a playback device may send the request to jointhe media playback system to a particular device, or group of devices,that will facilitate the playback device joining the media playbacksystem. For instance, the playback device may send a request to thedevice base, which may cause the device base to send (or request anotherdevice to send) configuration information and/or network parameters tothe playback device. In further example, the playback device may sendthe request to control devices of the media playback system, which mayfacilitate the playback device joining the media playback system. In yetfurther examples, the playback device may send the request to playbackdevices of the media playback system, which may facilitate the playbackdevice joining the media playback system.

To illustrate an example request, FIG. 8 depicts an example message flowin which playback device 106 of FIG. 7 is placed upon device base 132 tojoin playback device 106 to media playback system 100B. In this exampleimplementation, playback device 106 broadcasts an ALIVE 802 message,which indicates a request to join media playback system 100B. ALIVE 802message is received by control device 126. Control device 126 may listenfor ALIVE messages when in a particular mode (e.g., a set-up mode) orgenerally during operation. In an effort to transmit a request to joinmedia playback system 100B (i.e., the ALIVE message), playback device106 may repeatedly broadcast the ALIVE message for a period of time.Further, the playback device may transmit the ALIVE message at differentfrequencies (e.g., 2.4 Ghz and 5 Ghz), so as to communicate with devicesthat might be listening on a particular frequency.

Once control device 126 receives the ALIVE 802 message, it responds bysending a QUERY 804 message to another playback device of media playbacksystem 100 (i.e., playback device 104). One purpose of the QUERY 804message is to determine whether a media playback system has already beenestablished. If no response is received to such a message, a controldevice may establish a new media playback system that includes thecontrol device and the playback device that transmitted the ALIVEmessage.

After receiving the QUERY 804 message, playback device 104 sends aRESPONSE 806 message back to controller 126. The RESPONSE 806 messagecontains the name of media playback system 100B and the networkparameters (e.g., SSID, frequency, channel, etc) of the network thatinterconnects the devices of media playback system 100B. Based onreceiving the RESPONSE 806 message, control device 126 may determinethat media playback system 100B exists and operate accordingly.

In particular, control device 126 may engage in a key exchange withplayback device 106 (via QUERY 808 and a RESPONSE 810 message). Afterthe key exchange, control device 126 provides the configuration andnetwork parameters of media playback system 100B to playback device 106in SET 812 message. Playback device 106 may acknowledge this messagewith an ACK 814 message to playback device 106.

While FIG. 8 presents an example implementation of a request to join amedia playback system, other implementations are possible. For instance,a playback device that is joining a media playback system maycommunicate directly with a playback device of that media playbacksystem, rather than through a control device, as described in FIG. 8.Or, as another example, a different message flow may occur, such as amessage flow associated with another protocol (e.g., the WAC protocol).Yet further, a playback device may transmit a request to join the mediaplayback system to the device base.

As noted above, in some cases, a media playback system may requireconfirmation before permitting the playback device to join the mediaplayback system. A device of the media playback system may implementsuch authorization. For instance, prior to providing configuration andnetwork parameters to a playback device, a control device may determinewhether the playback device is authorized. In some cases, thisauthorization may involve checking a password or authorization tokenprovided by the playback device. In other cases, this authorization mayinvolve displaying a prompt that requests confirmation that the playbackdevice should be added to the network. In some cases, the control devicemay obtain confirmation more generally by way of a configured setting(e.g., a setting to allow (or prohibit) automatic joining of dockedplayback devices).

FIG. 9 depicts a control device 900 (e.g., a smartphone) that includesone or more processors, a tangible computer-readable memory, a networkinterface, and a display. Control device 900 is displaying an examplecontrol interface 902. Control interface 902 includes a prompt 904 thatindicates that a playback device is attempting to join the mediaplayback system. By selecting selectable control 906, the playbackdevice may be permitted to join the media playback system. Or, byselecting selectable control 908, the playback device may be prohibitedfrom joining the media playback system. Further, by selecting selectablecontrol 910, playback devices may be generally permitted to join themedia playback system when placed on a device base of the media playbacksystem.

d. Receive Message(s) that Enable the Playback Device to Join the MediaPlayback System

In FIG. 6, at block 608, implementation 600 involves receiving one ormore messages that enable the playback device to join the particularmedia playback system. For instance, referring to FIG. 5, playbackdevice 500 may receive a message that indicates configuration and/ornetwork parameters. By adopting such parameters, the playback device mayjoin the media playback system that is associated with device base 502.As another example, referring to FIG. 8, control device 126 provides theconfiguration and network parameters of media playback system 100B toplayback device 106 in SET 812 message. Such a SET message may enableplayback device 106 to join media playback system 100B, as theconfiguration and network parameters may enable the playback device toconnect to the network that interconnects devices of media playbacksystem 100B and to operate with those devices as part of media playbacksystem 100B. Example operations performed as part of a media playbacksystem are provided above in connection with the example operatingenvironments, as well as generally throughout the specification.

Receiving the one or more messages that enable the playback device tojoin the media playback system may involve sending a message orinstruction that causes the playback device to join a particular zone ofthe media playback system to which the device base is associated. Forinstance, a given device base may be associated with a Living Room zonesuch being placed on that device base causes the playback device to jointhe Living Room zone. In some embodiments, the playback device may sendan identifier of the base to the media playback system, perhaps with therequest to join the media playback system. The identifier of the basemay indicate to the media playback system that the playback device is onthat particular base, which may cause the media playback system to senda message that enables or causes the playback device to join the zonethat is associated with that base.

As a member of a zone, a playback device may operate as a functionalunit. For instance, the zone may have its own pre-existing queue, whichthe playback device may adopt as its own queue. The zone may also have apre-existing configuration defining certain operating parameters, whichthe playback device may adopt. For instance, the zone may have aparticular equalization, which the playback device adopts upon joiningthe zone. Further examples related to zones of a media playback systemare provided above in connection with the example operating environment,as well as generally throughout the specification.

In some cases, a zone may include multiple playback devices. In someconfigurations, receiving the one or more messages that enable theplayback device to join the media playback system may involve sending amessage or instruction that causes the playback device to assume aparticular role within the zone. For example, an example message maycause a playback device to operate as a left channel of a stereo pair.Another example message may cause the playback device to operate as asurround channel of a surround sound configuration.

As a member of a zone, a playback device may operate as a functionalunit with other playback devices of one or more additional zones thathave been joined together into a zone group. By enabling or causing theplayback device to join a zone, a message may also cause the playback tojoin a zone group. For instance, a Living Room zone and a Den zone maybe joined together into a “Living Room+Den” zone group. As a zone group,the playback devices of both zones may play media in synchrony with oneanother. These playback devices may share the same queue and may alsoadopt the same configuration.

As noted above, some playback devices may implement a queue, such thatthey are configured to playback media items from the queue. Further, azone of a media playback system may be associated with a queue such theplayback device of the zone plays back media items from that queue ofthe zone. In such embodiments, by joining a zone, the playback devicemay adopt the pre-existing queue of the zone that is associated with thezone property. Adopting the queue may involve populating the queue ofthe playback device with the media items that are queued in the queue ofthe zone, perhaps by receiving an indication of the zone's queue fromanother playback device of the zone. In some instances, the playbackdevice may remove any media items that were previously queued in itsqueue as part of adopting the queue of the zone, such that the playbackdevice has a queue that matches the queue of the zone.

As noted above, in joining a zone, a playback device may begin toperform operations jointly with other playback devices of the zone. Forinstance, the playback device may play back a queue (e.g., an adoptedqueue) of media items in synchrony with one or more additional playbackdevices of the zone. Further, a playback device may perform operationsjointly with playback devices of other zones that have been grouped intoa zone group with the zone of the playback device.

As a member of a zone or zone group, commands directed to the zone orzone group may be carried out by the playback device. For instance,commands to initiate or pause playback by the zone or zone group may becarried out by the playback device. Likewise, changes to the queue ofthe zone or zone group may be propagated to the playback device (e.g.,if a media item is queued in the zone's queue, the playback device mayplay back that media item when playback of the queue reaches that mediaitem).

Referring back to FIG. 7, playback devices 106, 108, 112, and 114 areplaced upon device bases 132, 134, 136, and 138, respectively. As notedabove, these playback devices may detect that they are placed uponrespective device bases of media playback system 100B and request tojoin media playback system 100B (perhaps given that they are configuredto do so). Upon making such a request, playback devices 106, 108, 112,and 114 may receive respective messages that enable the playback devicesto join the media playback system 100B. In some examples, such messagesmay enable playback devices 106, 108, 112, and 114 to join therespective zones that are associated with device bases 132, 134, 136,and 138, respectively (i.e., the Living Room, Dining Room, and Kitchenzones).

Upon being removed from a device base, a playback device may leave themedia playback system. For instance, referring to FIG. 5, playbackdevice 500 may detect its removal from device base 502 and responsivelydisjoin from the media playback system that is associated with devicebase 502. Leaving the media playback system may cause the playbackdevice to change configuration. For instance, the playback device may nolonger have the same configuration and network parameters as when theplayback device was part of the system. If the playback device hadadopted a queue, the playback device may dis-associate from that queue.Further, the playback device may no longer be configured to operatejointly with other devices of the media playback system. For example,control devices of the media playback system may no longer have controlover the playback device.

In some cases, the message that enables the playback device to join themedia playback system may include an instruction or other message thatcauses the playback device to join the media playback system while theplayback device remains on the playback device. Then, upon removal ofthe playback device from the device base, the playback device mayautomatically leave the media playback system. In other cases, themessage that enables the playback device to join the media playbacksystem may include an instruction or other message that causes theplayback device to remain with the media playback system even if theplayback device is removed from the device base. In such examples,access to the system by the playback device may be limited in otherways.

In some cases, a playback device may join a zone that does not currentlyinclude any other playback devices. In a sense, by joining such a zone,the playback device can be considered to have formed that zone. Byextension, by a playback device leaving the zone, the playback devicemay cause the zone to have no playback devices (given that no otherplayback devices had joined the zone since the playback device hadjoined that zone). However, the device base may retain its associationwith the zone, such that when a playback device is placed again on thedevice base, the zone may be formed again by that playback device whenthe playback device placed upon the device base.

By placing a playback device onto a device base and causing the playbackdevice to be assigned a zone property associated with a particular zone,the name of the playback device may be changed to the name of thatparticular zone. For example, a given device base may be associated witha Living Room zone. Upon being placed on that device base, a playbackdevice may join the Living Room zone, which may cause the name of theplayback device to be changed to “Living Room.” When the playback deviceis removed from that device base, the playback device may change itsname again (e.g., to “Portable”). Such name changes may indicate thatthe playback device is a member of a particular zone, or that theplayback device is operating as a portable device, among other examples.

In some embodiments, a playback device may join a media playback systemas a “guest” device when being placed on a device base that isassociated with the media playback system, but be more permanentlyregistered with a “home” media playback system. For instance, a user mayregister their playback device with their home media playback system(i.e., a first media playback system), but bring the playback deviceover to a friend's house for use as a “guest” device with the friend'smedia playback system (i.e., a second media playback system). Todistinguish a “guest” device from more permanently registered playbackdevices, such a guest device may be assigned a name that reflects theGuest status (e.g., “Guest Device” or “Guest). Control devices of themedia playback system may indicate this device name when indicating theguest device.

As a guest device of the second media playback system, the playbackdevice may adopt the configuration and/or network parameters of thesecond playback system, but store the configuration and/or networkparameters of the first playback system for later use. For example, uponleaving the second media playback system, the playback device mayre-adopt the configuration and/or network parameters of the firstplayback system. Alternatively, the playback device may re-adopt theconfiguration and/or network parameters of the first playback systemwhen back in range of the first media playback system.

Within examples, some media playback systems may restrict access to aplayback device that joins a media playback system based on being placedon a device base (e.g., as a guest device). For example, as noted above,such a playback device may be restricted to operating as part of a givenmedia playback system while the playback device remains placed upon thedevice base that is associated with the media playback system (which mayperhaps prevent the playback device from remaining in the media playbacksystem when operating as a portable (i.e., battery-powered) device). Asanother example, such a playback device may obtain registration on alimited basis. A limited registration with a media playback system maypermit the playback device to remain a part of the media playback systemfor a certain amount of time (e.g., a few hours) or for a limited numberof media item plays (e.g., playback of 20 media items). For example, aplayback device that is joined to a media playback system may determinethat the limited registration has expired (e.g., that a pre-determinedperiod of time has expired) and responsively leave the media playbacksystem.

The playback device may also be limited to certain media services. Forinstance, upon joining a media playback system as a guest (by beingplaced upon a device base), the playback device might not be able toaccess media services (e.g., streaming media services, such as Spotify®)that are registered with that media playback system. Instead, theplayback device may be able to access media services with which theplayback device's “home” media playback system is registered, which mayor might not include some of the same services. Note that even if thesame services are registered with two or more media playback system,each registration may be tied to a different account (e.g., accountsregistered to different email addresses or other user names).

IV. Example Techniques to Transfer Favorites Between Media PlaybackSystems

As discussed above, embodiments described herein may facilitate aplayback device joining a media playback system. In some examples, theplayback device may have favorites that were previously configured onthe playback device when the playback device was part of another mediaplayback system. When joining the media playback system, such favoritesmay be transferred (e.g., cross-linked) for use with the second mediaplayback system. FIG. 10 illustrates an example implementation 1000 bywhich a playback device transfers favorites for use with a second mediaplayback system.

a. Join a Playback Device Associated with a First Media Playback Systemto a Second Media Playback System

At block 1002, implementation 1000 involves joining a playback deviceassociated with a first media playback system to a second media playbacksystem. For instance, a playback device that was previously joined to afirst media playback system (e.g., a “home” media playback system) mayjoin a second media playback system (perhaps as a “guest” device). Insome examples, the playback device may join the second media playbacksystem upon being placed on a device base that is associated with thesecond media playback system, perhaps using techniques described abovein connection with implementation 600 of FIG. 6.

b. Identify One Or More Media Items Stored as Favorites Associated withthe First Media Playback System

In FIG. 10, at block 1004, implementation 1000 involves identifying oneor more media items that have been stored as favorites associated withthe first media playback system. A favorite may be any media item orcontainer of media items (track, album, playlist, or internet radiostation) that has been configured as a favorite. Each favorite mediaitem may be associated with a media source (e.g., a streaming media URIor local storage path) from which the media item can be retrieved andplayed back. An identifier of each favorite media item may be stored onthe playback device. A media playback system may identify such favoritemedia items associated with a playback device when the playback deviceis joined to the media playback system or when the favorite media itemis selected for playback, among other examples.

Such favorites may be accessible through a control interface (e.g.,buttons) on the playback device itself and/or through a controlinterface on a control device. For instance, an example control devicemay include five favorite buttons. Selection of a particular favoritebutton may cause the playback device to begin playing back a particularmedia item (e.g., a track, album, playlist, or internet radio station)from a particular source. Likewise, a control interface may include oneor more selectable controls which correspond to respective favoritemedia items. Such functionality may appear in practice to be similar toradio pre-sets that link to specific frequencies. However, instead oflinking to a frequency, the favorite control links to a network locationvia a path or URI. A URI, or uniform resource locator, may indicate asource of the media item from a streaming media service or other networklocation.

To illustrate, FIG. 11 depicts a playback device 1100, which may be anembodiment of playback device 200 of FIG. 2, among other examples.Playback device 1100 includes favorite buttons 1102A, 1102B, 1102C,1102D, and 1102E. Each of these favorite buttons may be configured tolink to a particular instance of a media item such that when the buttonis pressed, playback device 1100 begins playing the particular instanceof the media item from a given path or URI.

As another example, FIG. 12 depicts a control device 1200 (which isimplemented as a smartphone). Control device 1200 is displaying acontrol interface 1202 that includes controls for media playback system100B of FIG. 7. More particularly, control interface 1202 includes aplayback zone region 1204, a playback status region 1206, a favoriteregion 1208, and a playback control region 1210. A control interface,such as control interface 600A, may correspond to a particular device orzone of a media playback system (e.g., a Guest device or Guest zone of amedia playback system).

A playback zone region of a control interface may include arepresentation of the zone with which the control interface isassociated. As shown in FIG. 12, playback zone region 1204 includes anindication of a “Guest” zone of media playback system 100B, whichincludes a playback device that has joined media playback system 100Bupon being placed on a device base that is associated with mediaplayback system 100B.

Within examples, a playback status region includes a representation ofaudio content that is presently being played, previously played, orscheduled to play next in the Guest zone. Playback status region 1206includes contextual information about the “Guest” zone, includinginformation about media that is currently playing or queued by playbackdevice(s) of the zone. The information includes Album Art, Track Name,Artist Name, and Media Source, which represent metadata of the mediathat is currently playing or queued in the zone.

A favorite region includes controls to select favorites. As shown,favorite region 1208 includes five favorite controls. Each of thefavorite controls may be configured to link to a particular instance ofa media item such that when the control is selected, the Guest playbackdevice(s) begin playing the particular instance of the media item from agiven path or URI.

A playback control region includes transport controls for the zone.Playback control region 1210 includes transport controls for the “Guest”zone. Such controls may initiate, stop, or modify playback by playbackdevices the playback devices in the “Guest” zone.

c. Determine that Given Media Source of Media Item is Inaccessible toSecond Media Playback System

Referring back to FIG. 10, at block 1006, implementation 1000 involvesdetermining that a given media source of at least one favorite mediaitem is inaccessible to the second media playback system. In some cases,the favorites assigned to a given playback device may have beenconfigured when the playback device was joined to a first media playbacksystem (e.g., a “home” or “primary” media playback system). Upon beingplaced on a device base that is associated with a second media playbacksystem, the playback device may automatically join the second mediaplayback system. However, the second media playback system might nothave access to the same media sources as the first media playbacksystem, such that the favorite media items that were configured when theplayback device was joined to the first media playback system areinaccessible.

In some cases, to determine whether the respective media sources offavorite media items are accessible by the second media playback system,the second media playback system may attempt to access or retrieve(e.g., stream) the media item from the source that was associated withthe favorite by the first media playback system. If the playback deviceis able to access a favorite media item when joined to the second mediaplayback system, then it is determined that the media source of thefavorite media item is accessible to the second media playback system.Conversely, if the playback device is unable to access the favoritemedia item when joined to the second media playback system, then it isdetermined that the media source of the favorite media item isinaccessible to the second media playback system.

Alternatively, the second media playback system may determine whetherthe respective media sources of favorite media items are accessible bythe second media playback system via identifiers of the favorite mediaitems. Within examples, identifiers of each favorite may be stored asuniversal IDs (which identify the favorite across multiple sources) oras locally significant IDs (which identify the favorite across sourcesaccessible to a media playback system). Such identifiers may be storedon the playback device or in the cloud (i.e., on a server that isproviding a cloud service). To determine whether the respective mediasources of favorite media items are accessible by the second mediaplayback system, the second media playback system may search acrossmedia sources available to the second media playback system for suchidentifiers.

d. Identify a Second Instance of Media Item From Among Media SourcesAccessible to the Second Media Playback System

Referring again to FIG. 10, at block 1008, implementation 1000 involvesidentifying a second instance of the media item from among media sourcesaccessible to the second media playback system. The playback device mayconfigure a favorite button or control to play the second instance ofthe media item so as to cross-link the media item from a first source(accessible to the first media playback system) to a second source(accessible to the second media playback system) and possibly initiateplayback of the second instance of the media item (perhaps given thatthe favorite button or control was selected).

To identify the second instance of the media item, the media playbacksystem may search across media sources available to the second mediaplayback system. The media playback system may search by an identifierof the favorite media item, or by metadata, among other examples. Forinstance, a favorite might be linked to a playlist of media items from afirst media service (e.g., Spotify®). If the second system is notregistered with the first media service, the playback device may searchfor versions of the media items from one or more second services (e.g.,Apple Music® or Tidal®). In this way, the favorite may continue to linkto the same playlist of media items when the playback device is part ofthe second media playback system, but from one or more different sourcesthat are accessible to the second media playback system.

Certain media items might not need to be cross-linked. For instance,some media sources, such as Internet radio stations, may be universallyaccessible. Alternatively, the second media playback system may beregistered with the one or more of the same service(s) as the firstmedia playback system, such that the second media playback system canaccess the favorite media item from the same service as the first mediaitem. In such cases, some translation of the media source (e.g., URI)might be involved, as the second media playback system may access themedia item using a different user account or session identifiercorresponding to the second media playback system.

V. Second Example Techniques to Join a Playback Device to a Device Base

As discussed above, embodiments described herein may facilitate aplayback device joining a media playback system when placed onto adevice base. FIG. 13 illustrates an example implementation 1300 by whicha playback device joins a media playback system when placed upon adevice base that is associated with the device base.

a. Detect Placement of a Playback Device onto a Base

At block 1302, implementation 1300 involves detecting placement of aplayback device onto a base. For instance, referring back to FIG. 5,device base 502 detect placement of playback device 500 onto device base502.

In some embodiments, a device base may detect placement of a playbackdevice onto a base by way of a physical trigger. For instance, aplayback device may be designed to trigger a switch or other mechanismof the device base when a playback device is placed upon the devicebase. In such cases, by detecting triggering of the switch or mechanism,the device base detects placement onto the device base. As anotherexample, a device base may detect placement upon completing a circuitwith the playback device (such when charging a battery of the playbackdevice from a device base).

Alternatively, a device base may detect placement of a playback deviceby way of a radio signal between the playback device and the devicebase. For instance, the playback device and the device base may includerespective radio interfaces (e.g., near-field wireless communicationsinterfaces such as NFC (near field communications) or BLUETOOTH® LE). Adevice may detect placement of a playback device upon receiving amessage from the playback device.

As noted above, a device base may use a near-field wirelesscommunications interface, which may have a limited range such that theplayback device is in range of the device base when the playback deviceis placed on or nearby the device base. Shielding the antenna of such acommunications interface may further limit and orient its communicationsrange, which may prevent communications between a playback device and adevice base when the playback device is not on the device base.

b. Listen for a Request to Join Media Playback Systems

At block 1304, implementation 1300 involves listening for a request tojoin media playback systems. For instance, playback device 500 may senda request to join media playback systems or possibly to join aparticular media playback system to which device base 502 is associated.In some embodiments, playback device 500 may send such a requestautomatically, perhaps in response to detecting placement upon devicebase 502, or in response to determining that playback device 500 isconfigured to automatically join media playback systems. A device base502 may include a communications interface to listen for such requests.

In some implementations, the playback device may send the requestaccording to a particular protocol, such as SONOS® Netstart or APPLE®Wireless Accessory Configuration (WAC). In operation, a device base of amedia playback system may listen for messages conforming to such aprotocol. Further, such protocols may permit the playback device tocommunicate with the device base of the media playback system withoutbeing connected to the network that interconnects the devices of themedia playback system. By way of example, referring back to FIG. 8, aplayback device broadcasts an ALIVE message, which indicates a requestto join a media playback system. A device base may receive such amessage and take steps to join the playback device to the media playbacksystem.

So as to avoid continually looking for requests to join the mediaplayback system, the device base may listen for requests for apre-determined period of time (or less, if the device base receives sucha request). For instance, device base 502 may listen for 30 secondsafter detecting that a playback device has been placed upon device base502. If a request is not received during such a period, the device base502 may stop listening (and may put its communications interface in alow-power mode).

c. Send Request to Join the Playback Device to the Media Playback System

At block 1306, implementation 1300 involves sending a request to jointhe playback device to a media playback system. For instance, given thatdevice base 502 is associated with a particular media playback system,device base 502 may send a request to that media playback system (e.g.,to a control device or a playback device thereof) to join playbackdevice 500 to the particular media playback system. Such a request mayinclude any combination of the features described in connection withblock 606, among other examples.

d. Receive a Message Indicating that the Playback Device is Permitted toJoin the Media Playback System

At block 1308, implementation 1300 involves receiving a messageindicating that the playback device is permitted to join the mediaplayback system. For instance, device base 502 may receive configurationand/or network parameters from its media playback system, which mayindicate that the media playback system is permitting playback device500 to join the media playback system. As another example, device base502 may receive an instruction to provide configuration and/or networkparameters of the media playback system to playback device 500, whichmay indicate that playback device 500 is permitted to join the mediaplayback system.

e. Send a Message that Enables the Playback Device to Join the MediaPlayback System

At block 1310, implementation 1300 involves sending a message thatenables the playback device to join the media playback system. Forinstance, device base 502 may send a message indicating configurationand/or network parameters to playback device 500, which playback device500 may adopt to join the media playback system associated with devicebase 500. To further illustrate, referring back to FIG. 8, device base502 may send a SET message to playback device 500. Receiving such amessage may cause playback device to automatically join the mediaplayback system. Further examples related to such a message aredescribed above in connection with block 608 of FIG. 6.

VI. Conclusion

The description above discloses, among other things, various examplesystems, methods, apparatus, and articles of manufacture including,among other components, firmware and/or software executed on hardware.It is understood that such examples are merely illustrative and shouldnot be considered as limiting. For example, it is contemplated that anyor all of the firmware, hardware, and/or software aspects or componentscan be embodied exclusively in hardware, exclusively in software,exclusively in firmware, or in any combination of hardware, software,and/or firmware. Accordingly, the examples provided are not the onlyway(s) to implement such systems, methods, apparatus, and/or articles ofmanufacture.

The following examples set out further or alternative aspects of thedisclosure. The device in any of the following examples may be acomponent of any of the devices described herein or any configuration ofa device described herein.

(Feature 1) A playback device configured for:

detecting placement of the playback device onto a device base of aparticular media playback system, wherein the particular playback systemcomprises one or more additional playback devices;

determining that the playback device is configured to automatically joinmedia playback systems;

based on determining that the playback device is configured toautomatically join media playback systems, sending, to the particularmedia playback system, a request to join the particular media playbacksystem; and

receiving, from the media playback system, one or more messages thatenable the playback device to join the particular media playback system.

(Feature 2) The playback device of feature 1, wherein determining thatthe playback device is configured to automatically join media playbacksystems comprises determining that the playback device is not joined toany other media playback system.

(Feature 3) The playback device of any preceding feature, wherein theone or more control devices and the one or more additional playbackdevices of the particular media playback system are interconnected via anetwork, and wherein receiving the one or more messages that enable theplayback device to join the media playback system comprises receiving amessage that enables the playback device to connect to the one or morecontrol devices and the one or more additional playback devices of themedia playback system via the network.(Feature 4) The playback device of any of features 1-2, wherein thedevice base is assigned to a particular zone of the media playbacksystem, and wherein receiving the one or more messages that enable theplayback device to join the media playback system comprises receiving amessage that enables the playback device to join the particular zone ofthe media playback system to which the device base is assigned.(Feature 5) The playback device of feature 4, wherein enabling theplayback device to join the particular zone of the media playback systemcomprises causing the playback device to join a zone that consists ofthe playback device.(Feature 6) The playback device of feature 4, wherein enabling theplayback device to join the particular zone of the media playback systemcomprises causing the playback device to join a zone as a first channelof a stereo pair that includes an additional playback device as a secondchannel of the stereo pair.(Feature 7) The playback device of feature 4, wherein the particularzone is a first zone of a zone group that includes a second zone of oneor more given playback devices, and wherein receiving the one or moremessages that enable the playback device to join the media playbacksystem comprises receiving an instruction that causes the playbackdevice to join the zone group such that the playback device and the oneor more given playback devices are configured to playback media insynchrony.(Feature 8) The playback device of feature 4, wherein the particularzone is configured to play back media items from a pre-existing queue,and wherein joining the particular zone of the media playback systemcomprises adopting the pre-existing queue of media items as the queue ofthe playback device.(Feature 9) The playback device of any preceding feature, whereindetecting placement of the playback device onto the device base of theparticular media playback system comprises:

identifying the device base onto which the playback device is placed;and

determining that the identified device base is associated with theparticular media playback system of one or more additional playbackdevices.

(Feature 10) The playback device of feature 9, wherein sending therequest to join the particular media playback system comprisesbroadcasting a request indicating that the playback device is placedonto the identified device base which is assigned to the particularmedia playback system.(Feature 11) The playback device of feature 9, The playback device ofclaim 9, wherein identifying the device base onto which the playbackdevice is placed comprises receiving, from the device base, a signalindicating an identifier that uniquely identifies the device base.(Feature 12) The playback device of any preceding feature, wherein theplayback device is further configured for comprise charging a battery ofthe first playback device from current delivered through the particulardevice base while the playback device is placed on the particular devicebase.(Feature 13) The playback device of any preceding feature, whereinreceiving the one or more messages that enable the playback device tojoin the particular media playback system comprises receiving aninstruction that causes the playback device to join the particular mediaplayback system while the playback device remains on the device base.(Feature 14) The playback device of feature 13, wherein the playbackdevice is further configured for:

detecting removal of the playback device from the device base; and

responsively, disjoining the playback device from the particular mediaplayback system.

(Feature 15) The playback device of any preceding feature, whereinreceiving the one or more messages that enable the playback device tojoin the particular media playback system comprises receiving a messagethat enables the playback device to join the particular media playbacksystem for a pre-determined period of time, and wherein playback deviceis further configured for:

determining that the pre-determined period of time has expired; and

responsively, disjoining the playback device from the particular mediaplayback system.

(Feature 16) The playback device of any of features 1-15, wherein theparticular media playback system is a first media playback system; andwherein playback device is further configured for:

detecting selection of a selectable control that, when selected, causesthe playback device to play back a particular media item that has beenstored as a favorite of a second media playback system, wherein theselectable control is configured to play back the particular media itemfrom a given media source that is accessible to the second mediaplayback system;

determining that the given media source is accessible by the first mediaplayback system;

based on determining that the given media source is accessible to thefirst media playback system, playing back the particular media item fromthe media source.

(Feature 17) The playback device of any of features 1-15, wherein theparticular media playback system is a first media playback system; andwherein playback device is further configured for:

detecting selection of a selectable control that, when selected, causesthe playback device to play back a particular media item that has beenstored as a favorite of a second media playback system, wherein theselectable control is configured to play back a first instance of theparticular media item from a given media source that is accessible bythe second media playback system;

determining that the given media source is inaccessible by the firstmedia playback system; and

based on determining that the given media source is inaccessible by thefirst media playback system, identifying, among media sources that areaccessible by the first media playback system, a second instance of theparticular media item and playing back the second instance of theparticular media item from a media source that is accessible by thefirst media playback system.

(Feature 18) The playback device of any of features 1-15, wherein theparticular media playback system is a first media playback system; andwherein playback device is further configured for:

identifying a media item that has been stored on the playback device asa favorite of a second media playback system, wherein selection of aparticular selectable control of the playback device causes the playbackdevice to play a first instance of the media item from a given mediasource that is accessible to the second media playback system;

determining that the given media source is inaccessible to the firstmedia playback system;

based on determining that the given media source is inaccessible to thefirst media playback system, identifying, among media sources that areaccessible by the first media playback system, a second instance of themedia item and configuring the particular selectable control such thatselection causes the playback device to play the second instance of themedia item from a media source that is accessible to the first mediaplayback system.

(Feature 19) A device base comprising a base, the device base configuredfor

detecting placement of a playback device onto the base;

responsively, listening for a request to join media playback systems;

upon receiving the request to join media playback systems from theplayback device, sending, to a media playback system that is associatedwith the device base, a request to join the playback device to the mediaplayback system;

receiving, from the media playback system, a message indicating that theplayback device is permitted to join the media playback system; and

responsively, sending a message that enables the playback device to jointhe media playback system.

(Feature 20) The device base of feature 19, wherein the device base isinterconnected with the one or more control devices and the one or moreadditional playback devices of the particular media playback system viaa network, and wherein sending the message that enables the playbackdevice to join the media playback system comprises sending aninstruction that connects the playback device to the one or more controldevices and the one or more additional playback devices of the mediaplayback system via the network.(Feature 21) The device base of feature 19, wherein the device base isassigned to a particular zone of the media playback system, and whereinsending the message that enables the playback device to join the mediaplayback system comprises sending an instruction that causes theplayback device to join the particular zone of the media playback systemto which the device base is assigned.(Feature 22) The device base of feature 21, wherein enabling theplayback device to join the particular zone of the media playback systemcomprises causing the playback device to join a zone that consists ofthe playback device.(Feature 23) The device base of feature 21, wherein enabling theplayback device to join the particular zone of the media playback systemcomprises causing the playback device to join a zone as a first channelof a stereo pair that includes an additional playback device as a secondchannel of the stereo pair.(Feature 24) The device base of feature 21, wherein the particular zoneis a first zone of a zone group that includes a second zone of one ormore given playback devices, and wherein sending the message thatenables the playback device to join the media playback system comprisessending an instruction that causes the playback device to join the zonegroup such that the playback device and the one or more given playbackdevices are configured to playback media in synchrony.(Feature 25) The device base of feature 21, wherein the particular zoneis configured to play back media items from a pre-existing queue, andwherein enabling the playback device to join the particular zone of themedia playback system comprises causing the playback device to adopt thepre-existing queue of media items as the queue of the playback device.(Feature 26) The device base of any preceding feature, wherein thedevice base is further configured for charging a battery of the firstplayback device from current delivered through the base while theplayback device is placed on the base.(Feature 27) The device base of any preceding feature, wherein sendingthe message that enables the playback device to join the media playbacksystem comprises sending a message that enables the playback device tojoin the particular media playback system while the playback deviceremains on the base.(Feature 28) The device base of any preceding feature, wherein thedevice base is further configured for:

detecting removal of the playback device from the base; and

responsively, disjoining the playback device from the media playbacksystem.

(Feature 29) The device base of any of features 19-27, wherein sendingthe message that enables the playback device to join the particularmedia playback system comprises sending a message that enables theplayback device to join the particular media playback system for apre-determined period of time, and wherein the operations furthercomprise:

determining that the pre-determined period of time has expired; and

responsively, disjoining the playback device from the media playbacksystem.

(Feature 30) The device base of any of features 19-28, wherein sendingthe message that enables the playback device to join the particularmedia playback system comprises sending a message that enables theplayback device to join the particular media playback system until athreshold number of media items have been played back, and wherein theoperations further comprise:

determining that the threshold number of media items have been playedback; and

responsively, disjoining the playback device from the media playbacksystem.

(Feature 31) The device base of any of features 19-28, wherein sendingthe message that causes the playback device to join the particular mediaplayback system comprises sending a message that enables the playbackdevice to join the particular media playback system until a thresholdduration of playback time has elapsed, and wherein the operationsfurther comprise:

determining that the threshold duration of playback time has elapsed;and

responsively, disjoining the playback device from the media playbacksystem.

The specification is presented largely in terms of illustrativeenvironments, systems, procedures, steps, logic blocks, processing, andother symbolic representations that directly or indirectly resemble theoperations of data processing devices coupled to networks. These processdescriptions and representations are typically used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art. Numerous specific details are set forth to provide athorough understanding of the present disclosure. However, it isunderstood to those skilled in the art that certain embodiments of thepresent disclosure can be practiced without certain, specific details.In other instances, well known methods, procedures, components, andcircuitry have not been described in detail to avoid unnecessarilyobscuring aspects of the embodiments. Accordingly, the scope of thepresent disclosure is defined by the appended claims rather than theforgoing description of embodiments.

When any of the appended claims are read to cover a purely softwareand/or firmware implementation, at least one of the elements in at leastone example is hereby expressly defined to include a tangible,non-transitory medium such as a memory, DVD, CD, Blu-ray, and so on,storing the software and/or firmware.

We claim:
 1. A first playback device comprising: a first networkinterface; a second network interface; one or more audio transducers;one or more amplifiers configured to drive the one or more audiotransducers; one or more batteries; one or more processors; and ahousing carrying the first network interface, the second networkinterface, the one or more audio transducers, the one or moreamplifiers, the one or more batteries, the one or more processors, anddata storage having stored therein instructions executable by the one ormore processors to cause the first playback device to perform functionscomprising: adopting a first configuration, wherein the first playbackdevice is connected via the first network interface with a mobile deviceover a first network while the first configuration is adopted; playingback audio content via the one or more audio transducers and the one ormore amplifiers while connected via the first network interface with themobile device over the first network, wherein playing back audio contentin the first configuration comprises streaming data representing theaudio content via the first network interface from the mobile device;detecting connection of the first playback device to a device base;while the first playback device is on the device base, detectingconnection via the second network interface to a second network;adopting a second configuration that is different from the firstconfiguration, wherein the first playback device forms a stereo pairwith a second playback device over the second network while the secondconfiguration is adopted; and while in the stereo pair with the secondplayback device over the second network, playing back a first channel ofaudio content via the one or more audio transducers and the one or moreamplifiers in synchrony with the second playback device playing back asecond channel of the audio content, wherein playing back audio contentwhile in the stereo pair with the second playback device over the secondnetwork, comprises streaming data representing the audio content via thesecond network interface from one or more servers of a streaming mediaservice.
 2. The first playback device of claim 1, wherein first networkinterface is 802.15-compatible and the first network is a wirelesspersonal area network, and wherein the second network interface is802.11-compatible and the second network is a wireless local areanetwork.
 3. The first playback device of claim 1, wherein the firstplayback device configured to draw current from the one or morebatteries while the first configuration is adopted, and wherein thefirst playback device is configured to charge the one or more batteriesfrom current drawn via the device base while the second configuration isadopted.
 4. The first playback device of claim 1, wherein detectingconnection of the first playback device to the device base comprisesdetecting that current is being drawn through a charging circuit of thefirst playback device, wherein the charging circuit is configured tocharge the one or more batteries.
 5. The first playback device of claim1, wherein the functions further comprise: receiving data representinginstructions to enable a particular setting to automatically join thestereo pair while the second configuration is adopted; and based onreceiving the data representing instructions to enable the particularsetting to automatically join the stereo pair the second configurationis adopted, enabling the particular setting, wherein adopting the secondconfiguration comprises adopting the second configuration based on theparticular setting being enabled.
 6. The first playback device of claim1, wherein the functions further comprise: while the secondconfiguration is adopted, receiving, via the second network interfaceover the second network from the mobile device, instructions to playback the audio content while the second configuration is adopted.
 7. Thefirst playback device of claim 1, wherein adopting the secondconfiguration comprises: adopting the second configuration based ondetecting connection via the second network interface to the secondnetwork.
 8. The first playback device of claim 1, wherein the mobiledevice is incompatible with connection to the device base.
 9. The firstplayback device of claim 1, wherein when the first playback device isstreaming data representing the audio content via the first networkinterface from the mobile device, the mobile device streams datarepresenting the audio content via a network interface of the mobiledevice from the one or more servers of the streaming media service. 10.A method to be performed by a first playback device, the methodcomprising: adopting a first configuration, wherein the first playbackdevice is connected via a first network interface with a mobile deviceover a first network while the first configuration is adopted, andwherein the first playback device comprise a housing carrying the firstnetwork interface, a second network interface, one or more audiotransducers; one or more amplifiers configured to drive the one or moreaudio transducers; and one or more batteries; playing back audio contentvia the one or more audio transducers and the one or more amplifierswhile connected via the first network interface with the mobile deviceover the first network, wherein playing back audio content in the firstconfiguration comprises streaming data representing the audio contentvia the first network interface from the mobile device; detectingconnection of the first playback device to a device base; while thefirst playback device is on the device base, detecting connection viathe second network interface to a second network; adopting a secondconfiguration that is different from the first configuration, whereinthe first playback device forms a stereo pair with a second playbackdevice over the second network while the second configuration isadopted; and while in the stereo pair with the second playback deviceover the second network, playing back a first channel of audio contentvia the one or more audio transducers and the one or more amplifiers insynchrony with the second playback device playing back a second channelof the audio content, wherein playing back audio content while in thestereo pair with the second playback device over the second network,comprises streaming data representing the audio content via the secondnetwork interface from one or more servers of a streaming media service.11. The method of claim 10, wherein first network interface is802.15-compatible and the first network is a wireless personal areanetwork, and wherein the second network interface is 802.11-compatibleand the second network is a wireless local area network.
 12. The methodof claim 10, wherein the first playback device configured to drawcurrent from the one or more batteries while the first configuration isadopted, and wherein the first playback device is configured to chargethe one or more batteries from current drawn via the device base whilethe second configuration is adopted.
 13. The method of claim 10, whereindetecting connection of the first playback device to the device basecomprises detecting that current is being drawn through a chargingcircuit of the first playback device, wherein the charging circuit isconfigured to charge the one or more batteries.
 14. The method of claim10, further comprising: receiving data representing instructions toenable a particular setting to automatically join the stereo pair whilethe second configuration is adopted; and based on receiving the datarepresenting instructions to enable the particular setting toautomatically join the stereo pair the second configuration is adopted,enabling the particular setting, wherein adopting the secondconfiguration comprises adopting the second configuration based on theparticular setting being enabled.
 15. The method of claim 10, furthercomprising: while the second configuration is adopted, receiving, viathe second network interface over the second network from the mobiledevice, instructions to play back the audio content while the secondconfiguration is adopted.
 16. The method of claim 10, wherein adoptingthe second configuration comprises: adopting the second configurationbased on detecting connection via the second network interface to thesecond network.
 17. The method of claim 10, wherein the mobile device isincompatible with connection to the device base.
 18. The method of claim10, wherein when the first playback device is streaming datarepresenting the audio content via the first network interface from themobile device, the mobile device streams data representing the audiocontent via a network interface of the mobile device from the one ormore servers of the streaming media service.
 19. A tangible,non-transitory computer-readable medium having stored thereininstructions executable by one or more processors to cause a firstplayback device to perform functions comprising: adopting a firstconfiguration, wherein the first playback device is connected via afirst network interface with a mobile device over a first network whilethe first configuration is adopted, and wherein the first playbackdevice comprise a housing carrying the first network interface, a secondnetwork interface, one or more audio transducers; one or more amplifiersconfigured to drive the one or more audio transducers; and one or morebatteries; playing back audio content via the one or more audiotransducers and the one or more amplifiers while connected via the firstnetwork interface with the mobile device over the first network, whereinplaying back audio content in the first configuration comprisesstreaming data representing the audio content via the first networkinterface from the mobile device; detecting connection of the firstplayback device to a device base; while the first playback device is onthe device base, detecting connection via the second network interfaceto a second network; adopting a second configuration that is differentfrom the first configuration, wherein the first playback device forms astereo pair with a second playback device over the second network whilethe second configuration is adopted; and while in the stereo pair withthe second playback device over the second network, playing back a firstchannel of audio content via the one or more audio transducers and theone or more amplifiers in synchrony with the second playback deviceplaying back a second channel of the audio content, wherein playing backaudio content while in the stereo pair with the second playback deviceover the second network, comprises streaming data representing the audiocontent via the second network interface from one or more servers of astreaming media service.
 20. The tangible non-transitorycomputer-readable medium of claim 19, wherein the first networkinterface is 802.15-compatible and the first network is a wirelesspersonal area network, and wherein the second network interface is802.11-compatible and the second network is a wireless local areanetwork.
 21. A system comprising a first playback device and a secondplayback device, the system configured to perform functions comprising:adopting a first configuration, wherein the first playback device isconnected via a first network interface with a mobile device over afirst network while the first configuration is adopted, and wherein thefirst playback device comprise a housing carrying the first networkinterface, a second network interface, one or more audio transducers;one or more amplifiers configured to drive the one or more audiotransducers; and one or more batteries; the first playback deviceplaying back audio content via the one or more audio transducers and theone or more amplifiers while connected via the first network interfacewith the mobile device over the first network, wherein playing backaudio content in the first configuration comprises streaming datarepresenting the audio content via the first network interface from themobile device; detecting connection of the first playback device to adevice base; while the first playback device is on the device base, thefirst playback device detecting connection via the second networkinterface to a second network; the first playback device adopting asecond configuration that is different from the first configuration,wherein the first playback device forms a stereo pair with the secondplayback device over the second network while the second configurationis adopted; and while in the stereo pair with the second playback deviceover the second network, the first playback device playing back a firstchannel of audio content via the one or more audio transducers and theone or more amplifiers in synchrony with the second playback deviceplaying back a second channel of the audio content, wherein playing backaudio content while in the stereo pair with the second playback deviceover the second network comprises streaming data representing the audiocontent via the second network interface from one or more servers of astreaming media service.